Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[bitnami/mongodb] journal doesnt work anymore since 6.1 #65826

Closed
wants to merge 1 commit into from
Closed

[bitnami/mongodb] journal doesnt work anymore since 6.1 #65826

wants to merge 1 commit into from

Conversation

Xyvran
Copy link

@Xyvran Xyvran commented May 2, 2024 •
edited by carrodher
Loading

@Xyvran
journal doesnt work anymore
7059f88 
Signed-off-by: Xyvran <18017491+Xyvran@users.noreply.github.com>
@github-actions github-actions bot added mongodb triage Triage is needed labels May 2, 2024
@github-actions github-actions bot requested a review from javsalgar May 2, 2024 16:01
@carrodher carrodher added verify Execute verification workflow for these changes in-progress labels May 3, 2024
@github-actions github-actions bot removed the triage Triage is needed label May 3, 2024
@github-actions github-actions bot removed the request for review from javsalgar May 3, 2024 07:05
@github-actions github-actions bot requested a review from andresbono May 3, 2024 07:05
@andresbono andresbono changed the title journal doesnt work anymore since 6.1 [bitnami/mongodb] journal doesnt work anymore since 6.1 May 13, 2024
@andresbono
Copy link
Member

Hi, thank you for proposing this fix. I have some questions and comments:

  • How can I reproduce the issue? Although the setting you are removing is actually deprecated as per the info from #50109, is the application failing in some way when setting it? For compatibility with other old versions of MongoDB, it may be convenient to leave it there.
  • In case we agree with proceeding with the removal of this setting, shouldn't we go further with the changes are remove the references for that journal configuration and remove the env-var MONGODB_DEFAULT_ENABLE_JOURNAL and also apply the same changes for mongodb-sharded? The chart is also using this setting.

@github-actions GitHub Actions
Copy link

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.

@github-actions github-actions bot added the stale 15 days without activity label May 29, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Jun 4, 2024

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.

@github-actions github-actions bot added the solved label Jun 4, 2024
@andresbono andresbono closed this Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@andresbono andresbono Awaiting requested review from andresbono

Assignees

@andresbono andresbono

Labels
mongodb solved stale 15 days without activity verify Execute verification workflow for these changes
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[bitnami/mongodb-sharded] Unrecognized option: storage.journal.enabled when starting mongodb
4 participants
@Xyvran @andresbono @javsalgar @carrodher